Color processing arrangements with device independent color space conversion

ABSTRACT

A color processing method utilizing a plurality of devices having different color spaces as one virtual device. A scanner inquires a computer of color space and presence/absence of a color conversion function. If the computer has the color space conversion function, the scanner transmits color image data with parameters for converting the data into data of the color space of the computer. Inversely, the computer inquires the printer of color space and presence/absence of a color space conversion function. If the printer has the color space conversion function, the computer transmits color image data with parameters obtained from operation of parameters for converting the color space of the image data into the color space of the printer and the parameters received from the scanner.

BACKGROUND OF THE INVENTION

Present invention relates to a color processing method for correcting the difference among color spaces of color image input/output devices. The correction is performed when the output device such as a printer outputs a color image from e.g. a computer, when a color image is inputted into a computer from the input device such as a scanner or an electronic camera, or when a computer transmits color image data to another computer.

For example, even if various devices such as a computer, a scanner, an electronic camera and a printer can represent the same RGB color-components, each device has its own sensitivity to RGB color-components. For this reason, the printed results often disagree with the users' intention. Further, in a case where a single computer selectively uses a plurality of printers, color reproduction usually differs at each printer. In this case, the printed results may be different.

To avoid such inconvenience, a computer having high-operation capability performs appropriate color correction for each device. In case of an application software, it opens the menu so that the user can select necessary color space for a current printer/scanner.

However, the conventional color correction possesses the following drawbacks:

(1) As printers and scanners increase in varieties, difficulties in Color-Space-Selection occur on the application software side.

(2) The application software operator is in charge of correction, i.e., the user should perform color correction.

These problems are serious when sharing a plurality of scanners and printers by a plurality of computers via a network.

SUMMARY OF THE INVENTION

The present invention has been made in consideration of the above situation, and has as its object to provide a color processing method and color image processing apparatus which enables using a plurality of devices, each of which has its own color space, as one virtual device.

According to the present invention, the foregoing object is attained by providing a color processing method for a computer system having a plurality of device drivers respectively for image input/output devices and a plurality of color correction means for the input/output devices corresponding to the respective device drivers, the computer system processes color image data, comprising the steps of: performing color correction of the input/output devices by instructing the respective device drivers; and holding the color-corrected data by the respective device drivers.

Another object of the present invention is to provide a color processing method and apparatus which enables color space conversion with high-precision.

Still another object of the present invention is to provide a color processing method and apparatus which lowers load of a host computer.

Further object of the present invention is to provide an image processing system having a novel function and a device constituting the system.

Other features and advantages of the present invention will be apparent from the following description taken in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts throughout the figures thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

FIG. 1 is a block diagram schematically showing the system configuration of an embodiment of the present invention;

FIG. 2 illustrates a device driver in the embodiment;

FIG. 3 is a device-independent color space control protocol in the embodiment;

FIG. 4 illustrates Color-Space-Request packet used in the color space control protocol;

FIG. 5 illustrates Color-Space-List packet used in the color space control protocol;

FIG. 6 illustrates Color-Space-Select packet used in the color space control protocol;

FIG. 7 illustrates Color-Space-Select Ack packet used in the color space control protocol;

FIG. 8 is a block diagram showing the configuration of a server/client system to which the present embodiment is applied;

FIG. 9 is a block diagram showing in detail a client side of the server/client system;

FIG. 10 illustrates a general packet construction used in the color space control protocol;

FIG. 11 illustrates as an example-a signal sequence between the server and the client;

FIG. 12 illustrates in detail a signal sequence on a client side;

FIG. 13 illustrates as an example color correction in a monitor;

FIG. 14 illustrates as another example color correction in the monitor; and

FIG. 15 is a block diagram for explaining a color correction data control method.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of the present invention will be described in detail in accordance with the accompanying drawings.

Normally, connection between a computer and a printer is physical connection via e.g. a cable using a centronics interface. As is apparent from a network printer connected to a local area network (LAN), it is wrong to regard a cable as a "physical and logical" connecting point. A cable is a physical connecting point, however, if it is also a logical connecting point, an application software should be able to change the physical specification of each printer or scanner.

To avoid this problem, when an input/output device provided by an input/output device maker is connected to a computer, a device driver is installed into an operating system (OS) of the computer.

The present embodiment realizes an interface between the input/output devices such as printer and a scanner by virtualizing the following four items:

(1) Logical connecting point

(2) Standard color space

(3) Virtual color correction (virtual color space conversion)

(4) Virtual Color Space Conversion Protocol

Logical Connection!

FIG. 1 is a block diagram showing the system configuration embodying the present invention. In FIG. 1, reference numeral 1 denotes a scanner; 2, a connection cable; 3, a device driver of the scanner; 4, a computer; 5, an image processing application, e.g., a color DTP soft; 6, a device driver of printer 8; and 7, a connection cable. Device drivers 3 and 6 exist in the computer 4 and they are connected via programmable connection paths 9 and 10 to each other.

Conventionally, a color image data interface is defined by physical connecting points (cables 2 and 7) between the input/output devices 1 and 8. In the present embodiment, however, the interface is defined by logical connecting points (paths 9 and 10). More specifically, the device driver 3 exists in the computer 4 physically, however, the device driver 3 can be logically considered as a part of the scanner 1. Also, the device driver 6 which exists in the computer 4 physically can be regarded as a part of the printer 8.

Accordingly, the difference of color space between the computer 4 and the scanner 1 or the printer 8 can be easily corrected by using the interfaces 9 and 10 between the device drivers 3 and 6 as logical connecting points for color correction. The connection paths 9 and 10 will be referred to as "logical connecting points" hereinafter.

In this embodiment, the respective logical connections are provided with standard color space around them. If the computer 4 uses RGB color space and the printer 8 uses YMC color space, the device driver 6 performs RGB→YMC conversion.

Color Correction at Logical Connecting Point!

The color correction at a logical connecting point can be applied not only to the color space conversion between different color spaces, but to conversion between the same color spaces. For example, the scanner 1 normally outputs RGB signals and the computer 4 often uses RGB color space as its standard color space. In many cases, the white balance of the scanner 1 and that of the computer 4 are subtly different. Conventionally, the user has manually adjusted such subtle difference or has done nothing and abandoned the difference. Assuming that the color space of the scanner 1 is R'G'B', correction to the scanner 1 color space should be made by the device driver 3. That is, color correction should be preferably performed at a logical connecting point.

Introduction of Standard Color Space!

As described above, it is not appropriate to assume the color space of the scanner 1 "R'G'B'" and that of the computer 4 "RGB", since a well-designed standalone scanner performs color correction before it outputs a color signal. If the scanner color space RGB is standard, the computer 4 color space should be non-standard. Unfavorably, the misunderstanding that computers always have standard color space derives from the fact that they treat digital numerical values while scanners including a light source and a image sensor treat analog values. In fact, however, a color based on a value set on the computer is unknown until the data is displayed on a CRT display and becomes visible color to human eyes. For this reason, the computer numerical values cannot be determined correct unless the CRT display is properly adjusted. Usually, color correction is performed at the devices not in a computer, because the computer controls all the devices and therefore the color correction cannot be performed in the computer. In this case, however, the color correction is performed on the assumption that the computer has correct color space.

Contradiction in Color Correction by Computer!

As in many systems, it is convenient to perform final color correction by a computer. However, it is very incredible considering the above-mentioned fact that computer do not always have correct color space. For example, in an application software, a scanner can be driven using a command in the menu. It seems very convenient because the application can directly drive the scanner. In fact, a long list of scanners is displayed in the menu, then a corresponding scanner is selected, and scanning is started. As this selection is made only once, there seems no problem. However, problems occur in the following cases.

The scanner selection by the application software means the application softwares are in charge of setting the various scanners. Also color correction should be made by the application software. When there existed only a few types of black-and-white scanners in the market, an application software was able to perform color correction. Now there are variety of scanners such as a scanner for black-and-white half-tone and a color scanner, color correction by the application is insufficient. Device driver should clarify that the scanner side should be in charge of color correction. Even in a case where a system can provide only one scanner to a user, the system should have a construction connectable to a scanner of any type without adjustment.

Setting of Standard Color Space!

In the present embodiment, standard color space is provided at the logical connecting points in order to solve the above-mentioned problems and contradiction. Equation 1 is for converting color space "R'G'B'" into color space "RGB" f₁₁, f₁₂, . . . , f₃₃ ! is a conversion coefficient matrix. Equation 2 is for converting color space "RGB" into "rgb". g₁₁, g₁₂, . . . , g₃₃ ! is a conversion coefficient matrix.

Equation 3 is obtained by substituting the equation 1 into the equation 2. The conversion coefficient matrix of the equation 3 is replaced with equation 4, and the equation is expressed as equation 5. This means that once matrix operation is performed, the number of color conversion operations which should initially be performed twice can be reduced to once. The conversion coefficient matrices f₁₁, f₁₂, . . . , f₃₃ ! and g₁₁, g₁₂, . . . , g₃₃ ! are represented as F! and G! in equations 6 and 7 for the sake of simplicity. ##EQU1##

FIG. 2 shows the color space characteristics of the computer 4. In FIG. 2, the elements in FIG. 1 have the same reference numerals. Reference numeral 11 denotes a color space characteristic of the scanner; 12, a standard color space characteristic; 13, a color space characteristic of the computer. These color space characteristics are represented as "R'G'B'", "NTSC RGB", and "r'g'b'" respectively. "G" is a conversion means (matrix) for converting "R'G'B'" data into "NTSC RGB" data. "F" is a conversion means (matrix) for converting "NTSC RGB" data into "r'g'b'" data.

Any appropriate color space can be employed as the standard color space here. If the data transmitting side (scanner 3) and the receiving side (computer 5) both have "RGB" color space, it should be desirably "NTSC RGB". The transmitting side converts the device color space data "R'G'B'" into the standard color space data "NTSC RGB" by the conversion means "G". The receiving side converts the standard color space data "NTSC RGB" into the device color space data "r'g'b'" by the conversion means "F".

Virtual Color Correction (Virtual Color Space Conversion)!

The two conversion means "G" and "F" are indispensable for setting the standard color space. However, there are the following problems:

(1) The cost of the entire system increases.

(2) The throughput is degraded.

(3) Operation errors accumulate at every conversion.

(4) Color representation dynamic range becomes narrow at every conversion.

To avoid such problems, the Virtual Color Correction Concept (Virtual Color Space Conversion) is introduced in the present embodiment. The Virtual Color Correction/Virtual Color Space Conversion (hereinafter referred to as "virtual conversion") is a method for transmitting as one set an equation for converting color space into a target standard color space and initial data without operating the equation. In this method, the final operation is entrusted to the receiving side. The receiving side first operates the conversion means G and F, and multiplies the result with the initial data value. This reduces the number of the matrix operations (twice) to only once, and preventing operation errors such as a rounding error. Note that the operation is entrusted to the data receiving side only if the receiving side has the operation function. If the receiving side does not have the function, the operation is performed on the transmitting side.

Virtual Color Space Conversion Protocol!

FIG. 3 shows Virtual Color Space Conversion Protocol in the present embodiment. The communication between the transmitter and the receiver is performed via device drivers, and the protocol is realized by packet transmission. For example, in a case where the transmitter and the receiver perform communication within one personal computer, only a packet pointer is transmitted and an actual packet is not transmitted.

FIGS. 4 to 7 show the construction of respective packets. It should be noted that the constructions are similar to each other and therefore only Color-Space-Request packet shown in FIG. 4 will be described here. The packet includes one-byte base elements, packet ID 41, command ID 42, length 43, and content 44 from the top. The packet ID 41 has a code indicative of the type of the packet. The command ID 42 has a code indicating what the subsequent data elements represent. The length 43 shows the length of the content 44 in byte units. The command ID 42, the length 43 and the content 44 can be repeated depending upon circumstances. Terminator 45 is included at the end of the packet. The terminator 45 is a kind of command ID and is indicative of "0" The content 44 is a variable-length data whose length is defined in byte units by the length 43. Note that although the variable-length content 44 has expansivity, the content 44 can be fixed-length data.

The Virtual Color Space Conversion Protocol shown in FIG. 3 will be described below. First, the transmitter transmits the Color-Space-Request packet to the receiver, to specify the color space of image data to be transmitted and inquire of the receiver's color space. At the same time, the transmitter informs the receiver of presence/absence of a color conversion function. As shown in FIG. 4, the transmitter transmits data in accordance with "RGB" color space, and informs that there is no color conversion function ("No") on the transmitting side. On the other hand, the receiver returns a Color-Space-List packet to the Color-Space-Request packet, to inform the transmitter of a list of acceptable color spaces. As shown in FIG. 5, the receiver receives in accordance with "RGB" color space and informs that there is a color conversion function ("Yes") on the receiving side.

The transmitter transmits a Color-Space-Select packet as shown in FIG. 6 to determine the color space and data format to be used. For example, the employed color space data is "RGB" and the data is to be transmitted with virtual color correction parameters. This packet includes filter coefficients for color space correction. The receiver acknowledges the color space and the data format to be used by Color-Space-Select Ack packet as shown in FIG. 7. The transmission can be made without acknowledgment, and the Color-Space-Select Ack packet can be optional.

Next, a case where scanners and printers are connected to a computer via a network will be described. In this example, the transmitter is a Macintosh by Apple Computer (hereinafter referred to as "S/P Client"), the receiver is a standalone network scanner printer server (hereinafter referred to as "S/P Server"). In this system, the transmitter and the receiver are connected via a communication protocol. Generally, the Local talk is used for Macintosh, however, to have the machine coexist with e.g. the UNIX environment represented by the SUN, the TCP/IP protocol is suitable. For this reason, the MacTCP which is the TCP/IP protocol for Macintosh is employed as the communication protocol in this system.

The functional elements in this system are PrintTCP, the SP Client, the SP Server, and the MacTCP.

The PrintTCP and the SP Client and the MacTCP are installed into the Macintosh. The PrintTCP is a scanner printer driver for outputting data to a scanner printer server on the Ethernet via the TCP/IP from an application of the Macintosh. The basic functions of the PrintTCP is as follows:

(1) To generate, when the QuickDraw subroutine is called upon printing, a CaPSL (Canon Printing System Language) code equivalent to the subroutine. The CaPSL Is a printer language by Canon K. K.

(2) To generate, as a CaPSL code, bit map halftone image data (color/black-and-white) compressed by the ADCT (Adaptive Discrete Cosine Transformation) transformation based on the JPEG (Joint Photographic coding Experts Group) standards as an optional function.

(3) To transmit the generated CaPSL code to the S/P Server via the S/P Client driver.

The SP Client is a communication control program for transmitting a CaPSL code to the printer connected to the S/P Server via the TCP/IP and the Ethernet. The SP Client has the following basic functions:

(1) To link end-to-end the S/P Client and the S/P Server via the TCP/IP.

(2) To transmit CaPSL data received from the PrintTCP to the S/P Server.

(3) To have the S/P Server scan an original, then receive the scanned data, and transmit the received data to the application.

The SP Server always runs on the S/P Server as a demon, while waiting for data reception from the client. The basic functions of the SP Server are as follows:

(1) To pass the CaPSL data from the S/P Client to CaPSL interpreter.

(2) To start an original scanning program and transmit received scanned data to the S/P Client.

FIG. 8 shows the relation between these programs. The format and function of the resources of the respective program units are as follows:

(1) Printing Manager: to call a subsequent printer driver installed in the system as a standard driver. Type=DRVR, iPrDrvKef=-3

(2) PrintTCP: initially this printer driver is not installed in the system. It is provided as a code resource in the form of Chooser Document so as to be selected from the Chooser DA with Laser Writer and Image Writer.

(3) SP Client: this driver automatically installs itself in the system by INIT-31 mechanism upon starting of the system.

(4) MacTCP: this driver also has the resource "Control Panel Document". It sets initial values such as IP address from the control DA.

(5) SP Server: It is a FSX server side program which exists in the form of e.g. a demon of the UNIX.

In FIG. 8, reference numeral 20 denotes a DTP application on the market; 21, the Printing Manager which always exists in the OS; 22, the PrintTCP; 23, the SP Client; 24, the MacTCP; 25, an Ethernet board; 26, a control function of ADCT board; 27, an ADCT compression board; 28, an Ethernet Cable; 29, an Ethernet board; 30, the TCP/IP protocol which always exists in the UNIX; 31, the S/P server; 32, the CaPSL interpreter; 33, a control function of the ADCT board; 34, an ADCT compression board; and 35, the printer. Numerals 20 to 25 denote the Macintosh; 29 to 34, NWSP; 25 and 29, hardware for providing a communication function via the cable 28. Actual logical communication path can ensured by the MacTCP 24 and the TCPZIP 30. The SP Client 23 and the SP Server 31 form an end-to-end printer server/client protocol on a logical communication path provided by the TCP/IP 30. The purpose of this protocol is to serve as a driver to divert the application 50 from its attention to the network (Ethernet) and have the application regard the printer 35 as if it is connected to local computers. In other words, to the application 20, the printer 35 seems directly connected under the Printing Manager 21.

FIG. 9 shows in detail the relation between the computer side and the OS 36. As shown in FIG. 9, the Printing Manager 21 is a part of the OS 36. The PrintTCP 22 and the SP Client 23, the SP Client 23 and the Mac TCP, the PrintTCP and the control function 26 perform communication via a device manager 37. The PrintTCP 22 is divided into QuickDraw-CaPSL converter 22-1 and printer driver 22-2. The converter 22-1 replaces the QuickDraw subroutine with a CaPSL code. This operation enables the SP Server having the CapSL interpreter to emulate the QuickDraw in place of the QuickDraw. Constructing the system using the respective drivers as drivers not applications provides the greatest merit of easy standardization of specification, since the interface is connected via the OS 36. Further, if the OS is actually a single task OS, though the OS is the Multifinder, drivers at the corresponding parts can be multitasked. For example, in case of the UNIX, only an interface to a physical device can be a driver and the other interfaces can be demons to run on the background.

SP Client Format!

The SP Client driver automatically installs itself in the system by the INIT-31 mechanism upon turning on the power. When the driver memory size becomes greater, most codes are held in the form of code resource, and when the driver is opened, the resources are loaded on the system heap. In this case, the memory is freed when closing. The driver name begins with a period (".").

Further, the SP Client has the Control Panel Document resource. It can set various parameters such as the IP address from the Control Panel. For this purpose, it has resources as follows:

DITL ID=-4064

mach ID=-4064

nrct ID=-4064

ICN# ID=-4064

BNDL ID=-4064

FREF ID=-4064

cdev ID=-4064

Sp Client Driver Interface!

The SP Client provides the following hi-level deice manager routines:

DriverOpen

DriverClose

Control

FSRead

FSWrite

Status

KillIO

Other services of the SP Client than the above in the standard driver interface can be provided by Control routine. Various commands as listed below can be used by setting a cs code of the Control call's parameter block to a predetermined value:

SPSetInit

SPListen

SPCapability

Color-Space-Request

Color-Space-List

Color-Space-Select

Color Space Ack

Explanation of Commands!

The commands are as shown in table 1.

                                      TABLE 1                                      __________________________________________________________________________     DriverOpen                                                                           <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               host  host name                                                                wind  window size                                                                           (1,2,3,4)                                                         *buffer                                                                              buffer pointer                                                                        (SPOpen result)                                          return:  OsErr result                                                                   refnum                                                                               port ref.No.                                                                          (hereinafter this No.)                             DriverClose                                                                          <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                    return:  OsErr result                                                    FSRead                                                                               <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                             *buffer                                                                              buffer pointer                                                                        (received data buffer)                                   return:  OsErr result                                                                   RxSize                                                                               data size                                                                             (received data size)                                              EOF   End of File                                                                           data termination flag                              FSWrite                                                                              <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                             *buffer                                                                              buffer pointer                                                                        (transmission data                                                             buffer)                                                           size  data size                                                                             (transmission data                                                             size)                                                             EOF   End of File                                                                           (data termination                                                              flag)                                                    return:  OsErr result                                                    Status                                                                               <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               host  host name                                                                *buffer                                                                              buffer pointer                                                                        (SPStatus result)                                        return:  OsErr result                                                    Control                                                                              <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                             *buffer                                                                              buffer pointer                                                                        (data buffer)                                                     size  data size                                                                             (data size)                                              return:  OsErr result                                                    SPInit                                                                               csCode=cSpInit                                                                          server first issues it & prepares reception                           <item>   <define>                                                                             <content>                                                                             <example,comment.                                        parameter                                                                               host  host name                                                                Wind  window size                                                                           (1,2,4,8)                                                         *buffer                                                                              buffer pointer                                                                        (SPOpen result)                                          return:  OsErr result                                                                   refnum                                                                               port ref.No.                                                                          (hereinafter this No.)                             SPListen                                                                             csCode=cSPListen                                                                        server issues it & acknowledges reception                             <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                    return:  OsErr result                                                    SPSetStatus                                                                          csCode=cSPStatus                                                                        server issues it & changes S/P server setting                         <item>   <define>                                                                             <content>                                                                             <example,comment>                                        parameter                                                                               refnum                                                                               port ref.No.                                                             newStatus                                                                            new status                                                                     setting value                                                   return:  OsErr result                                                    __________________________________________________________________________

Packet Format!

General packet format of the SP Server/Client protocol is as shown in FIG. 10. In FIG. 10, numerals allotted at the left side indicates the number of bytes.

Packet Functions!

The functions of the SCCL packet and the DVCL packet are as shown in Tables 2 and 4.

                  TABLE 2                                                          ______________________________________                                         OpenConn                                                                                 set server/client link, ensure virtual                                         communication line                                                             inform server/client communication                                             function to opposite end                                             Open ConnReply                                                                           acknowledge server/client link                                                 acknowledge server/client link                                                 communication function                                                         establish connection number (Conn-ID)                                CloseConn                                                                                disconnect server/client link                                        Data                                                                                     data                                                                 Ack                                                                                      acknowledge data transmission                                        Nack                                                                                     acknowledge data transmission, control flow                          Status                                                                                   inquire of server/client link status                                 StatusReply                                                                              reply to Status; one of RR RNR Status ACK Abort                      Abort                                                                                    disconnect communication                                             Control                                                                                  control server/client (all services except                                     data to PrintTCP)                                                    ______________________________________                                    

                                      TABLE 3                                      __________________________________________________________________________     <DVCL Packet>                                                                  Init (com-id=fxInit)                                                                            :SPServer initialization request                              device=<device-name>                                                           direction=<data-direction>                                                                      (e.g. Print,Scan,Get,Give)                                    PDL=<language>   (e.g. CaPSL,Postscript,HPGL)                                  paper=<paper-size>                                                                              (e.g. A4, A3)                                                 scape=<scape-type>                                                                              (e.g. Landscape,Portrait)                                     resolution=<dpi> (e.g. 100,200,300,400)                                        color=<color-space>                                                                             (eg.BK,RGB,RGBX,CMYK,LAB,XYZ,YCrCb)                           InitAck(com-id=fxInitAck)                                                                       :SPServer initialization response                             result=<result-code>                                                                            (e.g. noErr,Error)                                            Scan(com-id=fxScan)                                                                             :scanning start request                                       paper=<paper-size>                                                                              (e.g. A4, A3)                                                 scape=<scape-type>                                                                              (e.g. Landscape,Portrait)                                     resolution=<dpi> (e.g. 100,200,300,400)                                        color=<color-component>                                                                         (e.g. R,G,B,C,M,Y,K,X,)                                       ScanAck(com-id=fxScanAck)                                                                       :scanning start response                                      result=<result-code>                                                                            (e.g. noErr,Error)                                            which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           Print(com-id=fxPrint)                                                                           :printing start request                                       paper=<paper-size>                                                                              (e.g. A4, A3)                                                 scape=<scape-type>                                                                              (e.g. Landscape,Portrait)                                     resolution=<dpi> (e.g., 100,200,300,400)                                       color-compo=<color-component>                                                                   (e.g. R,G,B,C,M,Y,K,X)                                        pages=<number-of-pages>                                                                         (e.g. 1-99)                                                   PrintAck (com-id=fxPrintAck)                                                                    :printing start response                                      result=<result-code>                                                                            (e.g. A4, A3)                                                 which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           queue-number=<number>                                                                           (e.g. 1,2,3 . . . all)                                        Capability(com-id=fxCapability)                                                                 :SPServer function acknowledgment                                              request                                                       CapabilityAck(com-id                                                                            :SPSserver function acknowledgment                            =fxCapabilityAck)                                                                               response                                                      device=<device-name>                                                           direction=<data-direction>                                                                      (e.g. Print,Scan,Get,Give)                                    PDL=<language>   (e.g. CaPSL,Postscript,HPGL)                                  paper=<paper-size>                                                                              (e.g. A4,A3)                                                  scape=<scape-type>                                                                              (e.g. Landscape,Portrait)                                     color=<color-space>                                                                             (e.g.BK,RGB,RFBX,CMYK,LAB,XYZ,YCrCb)                          SetArea(com-id=fxSetArea)                                                                       :original image effective area                                                 setting request                                               area=<print-area>                                                                               (e.g. top,lef,bottom,right)                                   SetAreaAck(com-id=fxSetAreaAck)                                                                 :original image effective area                                                 setting response                                              which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           result=<result-code>                                                                            (e.g. noErr,Error)                                            SetColor (com-id=fxSetColor)                                                                    :color designation request                                    which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           color=<color-space>                                                                             (eg.BK,RGB,RGBX,CMYK,LAB,YXZ,YCrCb)                           color compo=<color-component>                                                                   (e.g. R,G,B,C,M,Y,K,X)                                        SetColorAck(com-id=fxSetColorAck)                                                               :color designation response                                   result=<result-code>                                                                            (e.g. noErr,Error)                                            BufFlush(com-id=fxBufFlush)                                                                     :image memory clear request                                   which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           BufFlushAck(com-id=fxBufFlushAck)                                                               :image memory clear response                                  result=<result-code>                                                                            (e.g. noErr,Error)                                            __________________________________________________________________________

                  TABLE 4                                                          ______________________________________                                         ClearQueue(com-id                                                                               :printer queue clear request                                  =fxClearQueue)   (e.g. 1,2,3 . . . all)                                        queue-number=<number>                                                          ClearQueueAck(com-id                                                                            :printer queue clear                                          =fxClearQueueAck acknowledgment                                                result=<result-code>                                                                            (e.g. noErr,Error)                                            Comp(com-id=fxComp)                                                                             :image compression request                                    which-image=<image-id>                                                                          (e.g. 1, 2, 3 . . . )                                         type=<compression type>                                                                         (e.g. JPEG, MH,MR,MMR)                                        CompAck(com-ide=fxCompAck)                                                                      :image compression acknowledgment                             which-image=<image-id>                                                                          (e.g. 1,2,3 . . . )                                           result=<result-code>                                                                            (e.g. noErr,Error)                                            Decomp(com-id=fxDecomp)                                                                         :image expansion request                                      which image=<image-id>                                                                          (e.g. 1, 2, 3 . . . )                                         type=<compression type>                                                                         (e.g. JPEG,MH,MR,MMR)                                         DeCompAck(com-id=                                                                               :image expansion acknowledgment                               fxDeCompAck)     (e.g. 1,2,3 . . . )                                           which-image=<image-id>                                                                          (e.g. noErr,Error)                                            result=<result-code>                                                           DIR(com-id=fxDIR)                                                                               :directory request                                            DIRAck(com-id=fxDIRAck)                                                                         :directory response                                           director =<director>                                                                            (e.g. /home/user-name/file-name)                              CD(com-id=fxCD)  :directory change request                                     director=<director>                                                                             (e.g. /home/user-name/file-name)                              CDAck(com-id=fxCDAck)                                                                           :directory change response                                    result=<result-code>                                                                            (e.g. noErr,Error)                                            Get(com-id=fxGet)                                                                               :file transmission request                                    data=<data>                                                                    GetAck(com-ide=fxGetAck)                                                                        :file transmission acknowledgment                             result=<result-code>                                                                            (e.g. noErr,Error)                                            Put(com-id=fxPut)                                                                               :file reception request                                       data=<data>                                                                    PutAck(com-id=fxPutAck)                                                                         :file reception acknowledgment                                result=<result-code>                                                                            (e.g. noErr,Error)                                            Cancel(com-ide=fxCancel)                                                                        :scanner server operation, setting                                             cancellation                                                  result=<result-code>                                                                            (e.g. noErr,Err)                                              Color-Space-Request(com-id=                                                                     :transmitter's color space request                            Color-Space-Request)                                                                            and color processing function                                 Color Space      color space name                                              Capability       color processing capability                                   Color-Space-List(com-id=Color-                                                                  :receiver's color space list and                              Space-List       color processing function                                     Color-Space      color space name                                              Capability       color processing capability                                   Color-Space-Select(com-id=                                                                      :transmitter's color space                                    Color-Space-Select)                                                                             designation and color processing                                               method designation                                            Color-space      color space name                                              Color-Method     color processing method                                       Color-Space-Select Ack(com-id                                                                   :receiver's color space                                       =Color-Space-Select Ack)                                                                        acknowledgment and color                                                       processing method                                             Color-space      color space name                                              Color-Method     color processing method                                       ______________________________________                                    

FIGS. 11 and 12 show the sequence of these packets and commands. FIG. 11 depends upon the flow between a client and a server. FIG. 12 depends upon the flow between the MacTCP and the SP Client.

Similarly to standard file access, access from the application side are made using Open, Read, Write and Close commands. First, the PrOpen function is called from the application. The SP Client receives the SPOpen command, and it issues the TCPActivateOpen function by the Connect command to be connected with the TCP/IP. The SP Client indicates that the call of the TCP/IP has been normally set if the return of the function is "noErr". The SP Client subsequently transmits the OpenConn packet to the SP Server to link the SP Client and the SP Server on the set TCP link. The SP Server returns the OpenCopnnReply to acknowledge the setting of the session link unless there is no problem in the printer. Thereafter, the SP Client transmits the Init packet and the Control packet to the server side to initialize the parameters of the server side. Then, the SP Client issues the Color-Space-Request packet for color space control. The subsequent communication has been already described. These SP Server/SP Client packets are transmitted by TCPSend or TCPRv packets of the TCP/IP protocol.

Modification!

FIGS. 13 and 14 show a modification to the present embodiment. FIG. 13 shows image information displayed on a CRT monitor. In FIG. 13, reference numeral 50 denotes the CRT monitor; 51, a corrected color signal for displaying correct NTSC RGB color on the monitor; "D", a correction coefficient matrix; and 52, a connection cable. In order to display the RGB signal which is "proper" to human eyes, color correction such as gamma (γ) correction is required. In FIG. 13, gamma correction is performed on the computer side. As it takes a long period to perform such correction by a CPU, it is usually made on the monitor 50 side, as shown in FIG. 14. The scanner color signal is multiplied by the correction coefficient matrix D on the monitor side. Generally, a color correction circuitry of a monitor has a hardware construction, or it is a high-speed processor such as a DSP (Digital Signal Processor) for high-speed correction. In any case, to the computer side, the CRT has conventionally been a passive device which simply reproduces a given RGB signal. In other words, the coefficient matrix D has been the CRT monitor 50's own color processing system included in the monitor 50, and has never been directed to the computer for its dynamic use in frequent operation (except setting correction).

The device-independent color processing method according to the present invention can even omit the image processing operation by the CPU of the computer while the interface passes a color signal according to a virtual standard color space to the CRT monitor. Actually, the input-side color correction coefficients as the equation 4 and those of the scanner in FIG. 2 can be transmitted separately from the image signal, in the form of protocol, to the CRT monitor. Equation 8 shows this processing. "F" denotes a correction coefficient matrix for matching the scanner's own color space to the standard color space; 15 "G", a correction coefficient matrix in the Computer; and "D", a correction coefficient matrix for matching the monitor's own color space to the standard color space. If the CRT monitor is an active device as that in the present invention, the color correction operation can be made by the final device at a time as the equation 8.

In this manner, the present invention realizes a color processing system which optimizes hardware resource for high-speed operation while containing the device-independent concept, further, reduces accumulative errors of the operation.

It should be noted that the algorithm having cascade-connected filter operations so as to perform the operation at a time within the final device can be easily made when color correction is established between the three primary color representation (color mixing system) such as "RGB", "XYZ", "CMY" and "YIQ". However, in case of conversion between one of the above color systems and a color representation calculated from the XYZ system (color developing system) such as "L*a*b*", the operation based on the above algorithm cannot be performed easily. Rather, in such case, the color mixing system should be converted into the color developing system before operation.

Color Correction!

When a computer-processed color image is printed, whether the printed result coincides with the color on a CRT monitor or not is a significant problem. In a computer-processing system, the monitor and the printer are adjusted in the following manner.

In standard monitor adjustment, based on the assumption that the respective RGB color-components vary from 0 to 100, a "RGB=100,0,0" signal is inputted to display red, and the displayed red color is measured by a spectrophotometer. The measurement result obtained as a "XYZ" signal is converted into a RGB signal. The "R" signal gain is adjusted to "100, 0, 0". Similarly, a "RGB =100, 100, 100" signal is inputted and adjusts so that the output of the spectrophotometer will become "100, 100, 100". Next, a half tone color signal such as "RGB=70, 30, 30" is inputted and adjustment is performed in a similar manner, and finally, a signal "RGB=70, 70, 70" is inputted as white balance to complete adjustment. Regarding printer adjustment, the basis of the adjustment method is correspondent to the above method. It goes without saying that there are other applicable adjustment methods.

Once the monitor and the printer are respectively adjusted, the Corrected values become unchanged. Even through this adjustment stage, the CRT monitor display and the printed result may be different. Printing experts take this very seriously. To solve this problem, electronic color codes have been introduced. The electronic color codes are provided by printing ink makers, with computer color samples (color image data) so that colors the-same as their ink-printing color samples can be obtained on computer display. When a color image data is formed on a computer and finally printed out, referring to the electronic color codes is inevitable for the accuracy of the work. The electronic color codes are provided in the form of application, or provided as the document file of a popular application soft to be compared with attached color samples. Accordingly, the application's hue adjustment function requires minute adjustment. However, a plurality of applications, a plurality of ink makers, a plurality of color samples, and combinations thereof, will make such adjustment confusing.

Setting of adjustment values can be made by a utility program or by a DTP application. However, the adjustment results should not be managed by the application but by a device driver so as to avoid color correction for every color sample at every application. According to the embodiment, a color image signal passed to a device driver can be a virtual standard color. For this reason, the application side does not need to perform color matching, and the device driver itself performs it. The device driver manages color matching informations by saving them as color files of ink makers. The files can be changed over so that reference to the color samples in the same environment can be made from any application. In case of Macintosh, the device driver has cdev resources. This mechanism enables color correction from the Control Panel while operating an application, further, once-set values become common values to all the applications.

When using the device-independent color processing method according to the present invention, an application and a device driver can communicate with each other. In this case, the setting values of the device driver can be directly controlled from the application. FIG. 15 shows the relation between the direct control from the application. In FIG. 15, reference numeral 3 denotes a computer; 60, a printer; 61, a device driver for controlling the printer 60, which always exists in the computer 3; 62, a correction data file for a specific set of electronic color codes; and 63, a correction data file for a second set of electronic color codes. The device driver 61 directly uses the respective correction files, however, the application can indirectly use them, as shown in FIG. 15. Further, the correction files can be controlled from the cdev.

As described above, the device-independent color processing method enables color processing based on the standard color space to image data received from an input device, since the data is conceptually transmitted in accordance with virtual standard color space. Further, in this method, image data can be transmitted to an output device without color processing operation. Accordingly, a color processing system which improves the operation speed without accumulative errors such as rounding error, and optimizes hardware resource with maintaining the device-independent concept can be realized.

As described above, according to the present invention, a plurality of devices having different color space can be utilized as one virtual device.

The present invention can be applied to a system constituted by a plurality of devices, or to an apparatus comprising a simple device. Furthermore, it goes without saying that the invention is applicable also to a case where the object of the invention is attained by supplying a program to a system or apparatus.

The present invention is not limited to the above embodiments and various changes and modifications can be made within the spirit and scope of the present invention. Therefore, to apprise the public of the scope of the present invention, the following claims are made. 

What is claimed is:
 1. A color processing method for converting input color image data of a first color space depending on a first device into output color image data of a second color space depending on a second device, comprising the steps of:receiving, through a communication line from an external device, first color processing data for converting the first color space into a device independent color space; generating a third parameter by combining said first color processing data and second color processing data for converting the color image data in said device independent color space into color image data in the second color space; and performing color space conversion on the input color image data by using the third parameter to output color image data in the second color space.
 2. The method according to claim 1, wherein the color space is three primary color representation as a color mixing system such as RGB, XYZ, CMY and YIQ.
 3. The method according to claim 1, wherein the device independent color space is National Television System Committee (NTSC) RGB.
 4. The method according to claim 1, wherein, in said generating step, forth color processing data relating to a color correction according to tone characteristics of said second device is also combined with said first color processing data and said second color processing data.
 5. The method according to claim 1, wherein, in said receiving step, first color processing data stored in a packet is received based on a protocol between transmitting devices.
 6. The method according to claim 1, wherein said performing step is applied to said second device.
 7. The method according to claim 1, wherein said generating step is applied to said second device.
 8. The method according to claim 1, wherein said input color image data is received independent of said first color processing data, based on a protocol between transmitting sides, through a communication line from said external device.
 9. A color image processing system which has a transmission unit belonging to a first device and a receiving unit belonging to a second device, said transmission unit comprising:transmitting means for transmitting a first parameter for converting a first color space depending on the first device into a standard color space and color image data to said receiving unit through a communication line; and said receiving unit comprising: combining means for generating a third parameter by combining the first parameter and a second parameter for converting the standard color space of said receiving unit into a second color space depending on the second device; and color space conversion means for performing color space conversion for the color image data by using the third parameter.
 10. The system according to claim 9, wherein said first device is a scanner.
 11. The system according to claim 9, wherein said second device is a printer.
 12. The system according to claim 9, wherein said receiving unit is connected with the image processing apparatus via a connection point physically.
 13. A color processing apparatus for converting input color image data for a first color space depending on a first device into output color image data of a second color space depending on a second device, comprising:reception means for receiving, through a communication line form an external device, first color processing data for converting the first color space into a device independent color space; generating means for generating a third parameter by combining said first color processing data and second color processing data for converting the color image data in said device independent color space into color image data in the second color space; and color space conversion means for performing color space conversion on the input color image data by using the third parameter to output color image data in the second color space. 